Network Support Library

home *** CD-ROM | disk | FTP | other *** search

/ Network Support Library / RoseWare - Network Support Library.iso / btrieve / xtrdos.exe / XTRDOS.DOC < prev next >

Wrap

Text File | 1993-12-14 | 95.3 KB | 2,706 lines

NOVELL TECHNICAL INFORMATION DOCUMENT DOCUMENT PROCESSING INFO: NOVLIB LIB7 TITLE: Xtrieve DOS v4.1x patch E DOCUMENT ID: DOCUMENT REVISION: A DATE: 13DEC93 AUTHOR: MGAINES ALERT STATUS: Yellow DISTRIBUTION: Public INFORMATION TYPE: Issue README FOR: XTRDOS.EXE NOVELL PRODUCT CLASS: Database Products NOVELL PRODUCT and VERSION: Xtrieve PLUS 4.1x CATEGORY: DOS ABSTRACT: XTRDOS.EXE contains the DOS environment patch release E for Xtrieve PLUS v4.10 and v4.11a programs and utilities, the DOS environment patches for the XQLP v2.11a and XQLPO v2.11a programs, and the optional DOS environment patches for the XQLP and XQLPO programs. NOTE: In this document, XQLP and XQLPO are referred to collectively as XQLP(O). This patch is cumulative and includes updates for both v4.10 and v4.11. If you have Xtrieve PLUS v4.10, read this entire document. If you have Xtrieve PLUS v4.11, read "Installation Procedure" and then skip to "Xtrieve PLUS v4.11 for DOS." ================================================================================ Disclaimer and Copyright ======================== Novell(R), Inc. makes no representations or warranties with respect to the contents or use of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any NetWare software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of NetWare software, at any time, without any obligation to notify any person or entity of such changes. PATCH.EXE is a proprietary product of PocketSoft. PATCH.EXE and Patch Build generated files are distributed by Novell, Inc. under license from PocketSoft. Copyright (c) 1993 Novell, Inc. All rights reserved. ================================================================================ Contents ======== Installation Procedure Patch File Information Xtrieve PLUS v4.10 for DOS and XQLP(O) v2.11a Original File Information Xtrieve PLUS v4.10 Patch Set Descriptions December 1992 Patches XQLP(O) v2.11a Patch Set Descriptions December 1992 Patches XQLP(O) v2.11b Optional Patches December 1992 Patches Xtrieve PLUS v4.11 for DOS Original File Information Xtrieve PLUS v4.11 Patch Set Descriptions December 1992 Patches April 1993 Patches December 1993 Patches Documentation Updates December 1992 Updates Online Help Updates December 1992 Updates ================================================================================ Installation Procedure ====================== The PATCHXTR.BAT and PATCH.EXE files discussed in this procedure require DOS v2.1 or later. The Xtrieve PLUS for DOS patch set contains the following: - This Readme document - PATCH.EXE (a utility Novell provides for installing product patches) - PATCHXTR.BAT (a batch file to facilitate patch installation) - Patch files for Xtrieve PLUS (XTRIEVE.410 and XTRIEVE.411, which you use to patch versions 4.10 or 4.11) and for XQLP(O) (XQLP.21A and XQLPO.21A) - Replacement files (files with the same names as the files they replace) To update Xtrieve PLUS, complete the following steps: 1. Create a directory on your system, and copy the XTRDOS.EXE file to that directory. 2. Use the utility PKUNZIP.EXE to unzip the zipped files. 3. Install the patch files as follows: a. Refer to the list of patch files in the section of this Readme file entitled "Original File Information," find the original files on your system, and ensure that your original files match those listed. NOTE: This patch is cumulative; it contains all previous patches to Xtrieve PLUS v4.10 and Xtrieve PLUS v4.11. Whether you have the original XTRIEVE.EXE from the 4.10 release or from the 4.11 release, you will still apply the same patches. Again, please use the original file information specific to the version of Xtrieve PLUS you are patching. b. Use the DOS COPY command to copy the original file into the directory that contains the unzipped patch files from XTRDOS.EXE. c. Run PATCHXTR XTRDOS. (Entering PATCHXTR without any parameters displays a usage screen that lists all the parameters.) PATCHXTR verifies that you are patching the original released version of the software, applies the patch, and gives the original file an .ORG extension. d. Use the DOS COPY command to copy the patched file back to the original file's directory. 4. Install the replacement files as follows: a. Find the directory that contains the original files to be replaced. b. Before copying the replacement files, back up the original files to a diskette or to another directory. c. Use the DOS COPY command to replace the original files with the new files. 5. After applying the patches, you can remove the directory you created to store the XTRDOS.EXE file. You may also want to verify the version numbers when you load each program. The version numbers should match those listed in the next section, "Patch File Information." IMPORTANT: As mentioned above, if you patch v4.10, your current version of Xtrieve PLUS becomes v4.11a. When you are ready to patch v4.11, perform Steps 3 through 5 again, using the information provided for Xtrieve PLUS v4.11. =============================================================================== Patch File Information ====================== Patch Set Filename: XTRDOS.EXE Date: 12-13-93 Files Included: XTRDOS DOC This document XTRDOS TXT Short Readme PATCH EXE 76981 1-30-92 5:00a PATCHXTR BAT 3928 12-17-92 3:55p XQLOPT EXE 26582 12-13-93 2:53p Patch Files: XTRDOS 410 v4.11 146529 9-18-92 2:42p XTRDOS 411 v4.11e 85047 12-08-93 11:58a XQLP 21A v2.11b 270 9-21-92 1:54p XQLPO 21A v2.11b 269 9-21-92 1:55p Replacement Files: MAKE_XTA EXE v4.11c 68784 11-19-93 12:57p XCFP EXE v4.11c 32304 11-19-93 12:52p XHFP EXE v4.11b 16672 12-08-92 7:29p XMENU EXE v4.11b 98960 12-08-92 7:28p XTRIEVE MSG 39077 11-18-93 1:38p XTRIEVE HLP 221184 3-20-92 5:48p XTRIEVE MEN v4.11c 13347 11-18-93 1:38p ================================================================================ Xtrieve PLUS v4.10 for DOS and XQLP(O) v2.11a ============================================= The following information pertains to the DOS environment patches for the Xtrieve PLUS v4.10 and XQLP(O) v2.11a programs and utilities. Original File Information ------------------------- To ensure you are patching the original files, compare the files to be patched with those in the following list. This list shows the byte size and the date and time stamps for the original release. Patch these files: XTRIEVE EXE v4.10 454848 8-14-91 11:23a XQLP EXE v2.11a 204752 8-18-91 1:34p XQLPO EXE v2.11a 223936 8-18-91 1:40p Replace these files: MAKE_XTA EXE v4.10 65712 7-16-91 7:20p XCFP EXE v4.10 44032 7-17-91 9:19a XMENU EXE v4.10 98912 7-16-91 8:28p XHFP EXE v4.10 16672 7-17-91 9:29a XTRIEVE MSG 38204 8-07-92 3:54p XTRIEVE HLP 211968 8-07-92 3:54p XTRIEVE MEN v4.10 13325 8-07-92 3:54p NOTE: You may have newer versions of the replacement files listed above that you received in a previous patch release. Replace those existing files with the files included in this current patch release. Xtrieve PLUS v4.10 Patch Set Descriptions ----------------------------------------- The following information pertains to the DOS environment patches for the Xtrieve PLUS v4.10 program. This section describes each patch in the patch set. (Note that only the December 1992 patch release included patches for Xtrieve PLUS v4.10.) The patch descriptions for the Xtrieve PLUS engine appear first, followed by those for the utilities. For each patch, the description includes one or more search strings. These search strings indicate areas in which you may encounter the problem that the patch addresses. The search strings may help you quickly determine whether the patch you need for a specific problem is included in this patch set. NOTE: In some cases, the text describes a problem or reported bug that the update does NOT fix. In those cases, use the workaround provided. * * * * * * * * * December 1992 Patches --------------------- The following information describes patches released in December 1992. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: FOOTERS, HEADERS, REPORT Problem Fixed by This Patch: This patch prevents Xtrieve PLUS report headers or footers with more than one line from overwriting each other. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: FILE_CREATION, PAGE, PREALLOC Problem Fixed by This Patch: Xtrieve PLUS uses the default page size (512 KB) if you selected the Review Definitions option before selecting Finished-Create. In this situation, Xtrieve PLUS may also fail to preallocate the specified number of pages. This patch ensures that Xtrieve PLUS uses the page size you specify, and also that Xtrieve PLUS preallocates the specified number of pages. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: BFLOAT, DISPLAY, FLOAT, MASK Problem Fixed by This Patch: This patch ensures that Xtrieve PLUS can redisplay the proper field values when a display mask is used for a field of type float/bfloat. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: SDF, TIME, TRANSLATE Problem Fixed by This Patch: This patch ensures that Xtrieve PLUS correctly translates time values to Standard Data Format (SDF). * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: GROUP, HANG, LOCK UP, MODIFY, NESTED Problem Fixed by This Patch: When a report contains nested groups, attempting to modify or remove the outer group's fields when no fields are defined causes the computer to lock up. This patch prevents the computer from locking up when you modify or remove fields within the outermost group. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: HANG, LOCK UP, RIGHTS, SECURITY Problem Fixed by This Patch: Your computer may lock up in the following situation: you have security installed on your dictionary files and are using the NetWare SQL Requester (NSREQ) to access your files, and you attempt to access file- or field-level rights for a user profile. This patch prevents the computer from locking up when you access the file- or field-level rights. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: PRINT, REPORT Problem Fixed by This Patch: A report may contain inaccurate information if any line in the report (except for the last line on the page) is exactly the width of the page. This patch ensures that the report contains accurate information. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: BIT, DEFINITIONS, OFFSET, PRINT Problem Fixed by This Patch: If a file definition includes several bit data type fields adjacent to each other, a file definition printout shows each bit field starting at a new offset. This patch corrects the placement of the bit fields. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: 25-LINE, BLANK, CHARACTERS, SCREEN, VGA Problem Fixed by This Patch: The following situations can occur in 25-line mode on a VGA monitor after you exit Xtrieve PLUS: - The screen goes blank, but you can still enter characters at the keyboard. - Keyboard characters are displayed as different characters on the screen. This patch prevents either of these conditions from occurring. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: EDIT, HEADING, MODIFY, TITLE Problem Fixed by This Patch: If you press Esc and then select Continue when editing or modifying a view with a defined title field, the title data and heading may disappear. If you refresh the screen, the data reappears, but not the heading. This patch corrects the problem, so that both the title data and heading are retained. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: EDIT, DISPLAY, STRING Problem Fixed by This Patch: When you are entering data into a file with several string fields, any data you enter in the second field does not appear on the screen when you move to the following field, although the data is actually present in the Btrieve file. This patch allows the data in the second field to appear as entered. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: RECALL, REPORT, STORE Problem Fixed by This Patch: If you create (or recreate) a view, you must first store and recall it before you can create and store a report for that view; otherwise, you cannot recall the report after recalling the view. This patch allows you to create a report based on a view without first storing and recalling the view. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: CHARACTER, ESCAPE, HEX, REPORT Problem Fixed by This Patch: In a report containing an @esc or an @hexXX instruction (in which the hexadecimal value of XX represents a nonprintable character), Xtrieve PLUS does not include either the Escape character or the nonprintable character in the report. This patch causes Xtrieve PLUS to include these characters in reports. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: CASE, DEFINITION, DUPLICATE, FIELD Problem Fixed by This Patch: Xtrieve PLUS does not detect duplicate field names that differ only in terms of case until you try to complete the file definition with either Finished-Create or Finished-Don't Create. This patch causes Xtrieve PLUS to warn you of the duplication when you initially define the duplicate field. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: HANG, LOCK UP, SECURITY, SHOW, USER Problem Fixed by This Patch: Requesting user security information from Xtrieve PLUS can produce the wrong information. Also, with a dictionary user base of 255 to 500 users, selecting the SECURITY/USER/Show option may cause your computer to lock up. This patch causes Xtrieve PLUS to display the proper information and prevents computer lockup. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: 123, 1-2-3, DATE, EXPORT, LOTUS Problem Fixed by This Patch: If you export dates to a Lotus 1-2-3 worksheet, dates before 9/17/89 may appear as negative values. This patch causes those dates to appear as positive values. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: EDIT, MODIFY, OUT OF LOCAL HEAP SPACE Problem Fixed by This Patch: When you attempt to modify the data in a view that is based on a long restriction, you receive the message "Out of Local Heap Space in Xtrieve." This patch allows you to modify the data. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: COMMAND FILE, MAKE, OWNER NAME Problem Fixed by This Patch: When you press F7 while running a command file in which you are prompted for an owner name for a particular file, Xtrieve PLUS does not display the Make option or all of the command files available. This patch ensures that Xtrieve PLUS displays the Make option and the complete menu of command files. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: 226, EDIT, REMOVE Problem Fixed by This Patch: If you are using the EDIT/Remove option and attempt to select all records, Xtrieve PLUS returns Status Code 226. This patch enables you to select all records in that situation. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: ABORT, CONFIRM, RESTRICTION Problem Fixed by This Patch: If you press Esc while defining a restriction, Xtrieve PLUS might not ask you to confirm that you want to abort the restriction definition. This patch ensures that Xtrieve PLUS asks for confirmation before proceeding. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: DICTIONARY, HANG, LOCK UP, SHOW, /W Problem Fixed by This Patch: If you select Show from the DICTIONARY menu after starting Xtrieve PLUS with the /W parameter set to 24, your computer locks up. This patch allows you to select Show in this situation. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: CONFIGURE, FONT, PRINT, REPORT, STYLE Problem Fixed by This Patch: Xtrieve PLUS uses the default font (Courier 10 pitch) if you select a proportional font or a downloaded font with the Style option of the CONFIGURE/PRINT menu. This patch ensures that Xtrieve PLUS prints your report using the font you specify. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: INDEX, OWNER NAME, SUPPLEMENTAL Problem Fixed by This Patch: This patch ensures that you can define a supplemental index for a file with a Btrieve owner name. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: BLANK, DATE, SDF, TRANSLATE Problem Fixed by This Patch: When translating data from SDF, Xtrieve PLUS replaces each blank date ( / / ) with the date from the preceding record. This patch ensures that Xtrieve PLUS properly translates blank dates. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: BTRIEVE, DICTIONARY, FIELD, SHOW Problem Fixed by This Patch: If your dictionary definition does not match the Btrieve file definition, Xtrieve PLUS displays incorrect field information when you use the DICTIONARY/Show option to examine the file's dictionary definition. This patch ensures that Xtrieve PLUS properly displays the field information * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: DATE, MASK, SDF, TRANSLATE, YEAR Problem Fixed by This Patch: When translating to Standard Data Format (SDF), Xtrieve PLUS translates date fields with a mask of mm/dd/yyyy as mm/dd/yy. When translating four-digit year masks from SDF, Xtrieve PLUS repeats the first two digits of the year. (For example, it translates 1992 as 1919.) This patch ensures that Xtrieve PLUS properly translates date fields to and from SDF. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: INDEX, JOIN, SEMICOLON, GARBAGE Problem Fixed by This Patch: Xtrieve PLUS displays graphic characters at the bottom of the screen when joining two files on an index that contains a semicolon (;). This patch enables Xtrieve PLUS to join files in this situation without displaying extraneous characters. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: LOGICAL, MASK, SDF, TRANSLATE, Y-N Problem Fixed by This Patch: When Xtrieve PLUS translates a logical type field with a mask of y-n to SDF, it translates all values as n. This patch ensures that Xtrieve PLUS properly translates the data. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: DIVIDE OVERFLOW, PRINT, REPORT Problem Fixed by This Patch: When you attempt to print a report to either a file or a printer, Xtrieve PLUS returns the message "Divide Overflow." This patch allows you to print a report to a file or a printer. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: 249, RECALL, STORE, VIEW Problem Fixed by This Patch: If you attempt to recall a view when more than 249 views are stored in VIEW.DDF, Xtrieve PLUS returns the message "There Are No Views Stored in This Dictionary." This patch allows you to recall a view in this situation. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: 228, COMMAND FILE, EDIT, FPROMPT Problem Fixed by This Patch: When attempting to execute the FPROMPT command in a command file, Xtrieve PLUS recalls the view to be edited but then returns Btrieve Status Code 228 (Invalid Data Length in Buffer) when you attempt to edit a field. Also, Xtrieve PLUS displays incorrect data in the field. This patch ensures that Xtrieve PLUS properly executes the FPROMPT command in command files. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: 1-2-3, LOTUS, REPORT, TIME, TRANSLATE Problem Fixed by This Patch: Xtrieve PLUS does not translate fields of data type time from reports to Lotus 1-2-3 worksheets. This patch ensures that Xtrieve PLUS can properly translate reports containing time fields to Lotus 1-2-3. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: FIELD NAME, JOIN Problem Fixed by This Patch: This patch ensures that Xtrieve PLUS properly joins files that contain identical field names. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: 209, DICTIONARY, FILE, MODIFY, SECURITY Problem Fixed by This Patch: If you attempt to use the SECURITY/MODIFY/File option when there are no data files defined and the SWITCHES/DICTIONARY/Show option is set to No, Xtrieve PLUS returns Status Code 209 instead of the error message "Dictionary is Empty." This patch ensures that Xtrieve PLUS returns the correct error message in this situation. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: ERROR WRITING OUTPUT, SDF, TRANSLATE, USER-DEFINED, ZSTRING Problem Fixed by This Patch: Xtrieve PLUS returns the message "Error Writing Output" when you attempt to translate a user-defined field of type zstring (using Left Chars or Right Chars function) to SDF. This patch ensures that Xtrieve PLUS properly translates zstring fields to SDF. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: 81, BROWSE, EDIT, HANG, LOCK UP, MODIFY Problem Fixed by This Patch: When you return to Browse mode from EDIT/Modify mode, Xtrieve PLUS does not release the multiple-record locks; consequently, Xtrieve PLUS returns Btrieve Status Code 81 (Lock Error) the next time you attempt to switch to EDIT/Modify mode. This patch ensures that Xtrieve PLUS releases multiple-record locks when you return to Browse mode from EDIT/Modify mode. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: HANG, JOIN, KEY, LOCK UP, PRIMARY Problem Fixed by This Patch: When you are joining two large files, basing the join on more than one primary field causes your computer to lock up. This patch ensures you can join files in this situation. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: GLOBAL, OUT OF LOCAL HEAP SPACE, RIGHTS, SECURITY, USER Problem Fixed by This Patch: When you add a user with global rights only, show that user's rights, press Esc, and then press F7 to record a command file, Xtrieve PLUS returns the message "Out of Local Heap Space in Xtrieve." This patch ensures you can perform this operation without receiving an error. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: COMMAND FILE, OUT OF LOCAL HEAP SPACE, SHIFT-F1 Problem Fixed by This Patch: When you replay a command file and then press Shift-F1 to select another command file to replay, Xtrieve PLUS returns the message "Out of Local Heap Space in Xtrieve." This patch ensures you can perform this operation without receiving an error message. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: DISPLAY, JOIN, TRUNCATE, VIEW Problem Fixed by This Patch: If you join several views together, return to the MAIN menu, and then access the view you created, Xtrieve PLUS truncates the list of joined views at the top of your view screen. This patch ensures that Xtrieve PLUS properly displays the list of joined views. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: DISPLAY, FIELD, SORT, USER-DEFINED, VIEW Problem Fixed by This Patch: If your sort is based on a user-defined field, Xtrieve PLUS incorrectly displays the field by which your view is sorted in the upper right corner of the definition window. This patch ensures that Xtrieve PLUS displays this information correctly. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: CONFIGURATION, HANG, LOCK UP, LOG IN, MASTER Problem Fixed by This Patch: If you use the Configuration option to log in as a different user after logging in as MASTER, your computer locks up. This patch allows you to perform this operation without locking up your computer. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: 284, ADD, CLEAR, FIELD, RECORD Problem Fixed by This Patch: If you attempt to add a record without one of the required fields, Xtrieve PLUS returns Btrieve Status Code 284 (Specified Value Is Not in List of Valid Values) and then clears all the information you entered. This patch ensures that Xtrieve PLUS does not clear the information you entered. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: 284, ATTRIBUTE, ERROR WRITING OUTPUT, TRANSLATE, VIEW Problem Fixed by This Patch: If you attempt to translate the current view to a retained view with an invalid field attribute, Xtrieve PLUS returns the message "Error Writing Output" instead of Btrieve Status Code 284 (Specified Value Is Not in List of Valid Values). This patch ensures that Xtrieve PLUS returns Status Code 284 in this situation. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: 99/, ADD, EDIT, INTEGER, MASK, RANGE Problem Fixed by This Patch: If you use the EDIT/Add option to enter data into an integer field with the mask 99/ and a range of '1'..'12', Xtrieve PLUS does not accept any entry in that field. This patch ensures that Xtrieve PLUS allows you to enter data in this situation. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: BROWSE, EDIT, FORM, OFFSET, REMOVE Problem Fixed by This Patch: Xtrieve PLUS does not correctly format data when you use the EDIT/Remove option following a FORM/Browse operation. This patch ensures that Xtrieve PLUS displays data at the correct offset. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: HANG, LOCK UP, MENU, OPERATOR, RESTRICTION, USER-DEFINED Problem Fixed by This Patch: Xtrieve PLUS locks up your workstation if you attempt to use a user-defined menu containing restriction operators that are longer than those supplied with Xtrieve PLUS. This patch ensures that you can use such a menu. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: CONDITIONAL, HANG, LOCK UP, FIELD, JOIN, NESTED, USER-DEFINED Problem Fixed by This Patch: If you create a nested, conditional, user-defined field in a joined view, your computer locks up. This patch ensures that Xtrieve PLUS returns the error message "Out of Local Heap Space in Xtrieve" instead of locking up your computer. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: 51, ENCRYPT, INVALID OWNER, OWNER NAME, SUPPLEMENTAL Problem Fixed by This Patch: If you add a supplemental index to an encrypted Btrieve file that requires an owner name for any access (ENCRYPT/Any), Xtrieve PLUS returns Status Code 51 (Invalid Owner). This patch ensures you can perform this operation without receiving Status Code 51. * * * * * * * * * Platform/Product: DOS - XTRIEVE.EXE, v4.10 Search Strings: CENTER, JUSTIFY, RIGHT Problem Fixed by This Patch: This patch ensures that you can right justify a field after you have center justified it. * * * * * * * * * Platform/Product: DOS - MAKE_XTA.EXE, v4.10 Search Strings: HANG, LOCK UP, MAKE_XTA, TRANSLATE, LARGE VIEWS Problem Fixed: If you attempt to use the MAKE_XTA utility to translate fields of large views, your computer locks up. This update ensures you can perform this operation. * * * * * * * * * Platform/Product: DOS - MAKE_XTA.EXE, v4.10 Search Strings: JOIN, MAKE_XTA, TRANSLATE Problem Fixed by This Patch: This update ensures that the MAKE_XTA utility properly translates joined views. * * * * * * * * * Platform/Product: DOS - MAKE_XTA.EXE, v4.10 Search Strings: MAKE_XTA, RESTRICTION, USER-DEFINED, VIEW Problem Fixed by This Patch: This update ensures that the MAKE_XTA utility can recall a view definition that includes a user-defined field or restriction. * * * * * * * * * Platform/Product: DOS - MAKE_XTA.EXE, v4.10 Search Strings: LAYOUT, MAKE_XTA, REPORT, SUMMARY, TRANSLATE, USER-DEFINED Problem Fixed by This Patch: This update ensures that the MAKE_XTA utility properly translates information from a report layout file with a user-defined summary field. * * * * * * * * * Platform/Product: DOS - XCFP.EXE, v4.10 Search Strings: COMMAND FILE, MOUSE, POSDIRECT, WINDOW, XCFP Problem Fixed by This Patch: This update ensures that the XCFP command file processor correctly interprets mouse commands with the window identifier POSDIRECT. * * * * * * * * * Platform/Product: DOS - XMENU.EXE, v4.10 Search Strings: MENU, XMENU, XTRIEVE.MEN Problem Fixed by This Patch: If you attempt to open XTRIEVE.MEN, the XMENU utility returns the message, "'XTRIEVE.MEN' File Is Not a Compatible Menu File for Xtrieve." This update ensures that XMENU recognizes XTRIEVE.MEN as a compatible menu file. * * * * * * * * * XQLP v2.11a and XQLPO v2.11a Patch Set Descriptions --------------------------------------------------- Note that only the December 1992 patch release included patches for XQLP v2.11a and XQLPO v2.11a. December 1992 Patches --------------------- The following information describes patches released in December 1992. * * * * * * * * * Platform/Product: XQLP for DOS - XQLP.EXE, v2.11a XQLPO for DOS - XQLPO.EXE, v2.11a Search Strings: FETCH, CURRENT Problem Fixed by This Patch: xFetch/XQLFetch CURRENT operations can skip the current record and return the next record that meets the restriction if the restriction is in the following format: "field = 'value' OR field = 'value' OR...." This patch ensures that xFetch/XQLFetch CURRENT operations return the current record in this situation. * * * * * * * * * Platform/Product: XQLP for DOS - XQLP.EXE, v2.11a XQLPO for DOS -XQLPO.EXE, v2.11a Search Strings: QUERY, TABLE, ALTER, HANG, LOCK UP Problem Fixed by This Patch: The workstation may hang when XQL attempts to execute a query against a view and then the tables used to create the view are altered. That is, the tables are defined, a view is created on the tables, the tables are altered, and the view (which is no longer applicable) is used, causing XQL to hang the workstation. This patch prevents the workstation from locking up. * * * * * * * * * Platform/Product: XQLP for DOS - XQLP.EXE, v2.11a XQLPO for DOS -XQLPO.EXE, v2.11a Search Strings: 3, GLOBAL DATA VARIABLE Problem Fixed by This Patch: If the record length of the first table in a view is greater than 2062 bytes, XQL may overwrite global data variables. One possible symptom of this problem is that Btrieve returns Status Code 3 (File Not Open) when XQL tries to access the dictionary files. This patch prevents XQL from overwriting global data variables in this situation. * * * * * * * * * Platform/Product: XQLP for DOS - XQLP.EXE, v2.11a XQLPO for DOS -XQLPO.EXE, v2.11a Search Strings: XREMALL, REJECT Problem Fixed by This Patch: If the reject count passed to xRemall is not -1, and xRemall returned because the maximum reject count was reached, your application may enter an infinite loop. Depending on the restriction and the contents of the data file, xRemall may continue to reject the same set of records without returning an end-of-file status. This patch prevents your application from entering an infinite loop in this situation. * * * * * * * * * XQLP(O) v2.11b Optional Patches ------------------------------- Note that only the December 1992 patch release included patches for XQLP(O) v2.11b. December 1992 Patches --------------------- Optional patches are available for XQLP(O) v2.11b. You can apply these patches only after applying the 2.11a patch set to the original 2.11a version of XQLP(O). You can find these optional patches in XQLOPT.EXE, which this patch set includes. ================================================================================ Xtrieve PLUS v4.11 for DOS ========================== The following information pertains to the DOS environment patches for the Xtrieve PLUS v4.11 programs and utilities. Original File Information ------------------------- To ensure you are patching or replacing the original files, compare the files to be patched or replaced with those in the following list. This list shows the byte size and the date and time stamps for the original release. Patch this file: XTRIEVE EXE v4.11 454848 8-14-91 11:23a Replace these files: MAKE_XTA EXE v4.11 65712 7-16-91 7:20p XCFP EXE v4.11 44032 7-17-91 9:19a XMENU EXE v4.11 98912 7-16-91 8:28p XTRIEVE MSG 39017 8-11-92 3:59p XTRIEVE HLP 221184 3-20-92 5:55p XHFP EXE v4.11 16672 6-25-92 5:47p XTRIEVE MEN v4.11 13347 8-11-92 3:59p Xtrieve PLUS v4.11 Patch Set Descriptions ----------------------------------------- The following information pertains to the DOS environment patches for the Xtrieve PLUS v4.11 program. This section describes each patch in the patch set. The patch descriptions for the Xtrieve PLUS engine appear first, followed by those for the utilities. For each patch, the description includes one or more search strings. These search strings indicate areas in which you may encounter the problem that the patch addresses. The search strings may help you quickly determine whether the patch you need for a specific problem is included in this patch set. NOTE: In some cases, the text describes a problem or reported bug that the update does NOT fix. In those cases, use the workaround provided. * * * * * * * * * December 1992 Patches --------------------- The following information describes patches released in December 1992. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: DISPLAY ERRORS Problem Fixed by This Patch: In the Report Layout screen, when you insert a field between two fields that take up a relatively large portion of the screen, Xtrieve PLUS redraws the screen incorrectly. This patch does not contain a fix; Xtrieve PLUS accurately stores the new data. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: F8, HANG, MODIFYING, REPORT LAYOUT Problem Fixed by This Patch: When you repeatedly use the key sequence Shift+F8, F8, and Esc when modifying or viewing groups or fields in a report layout, Xtrieve PLUS terminates. This patch ensures that Xtrieve PLUS properly closes and reopens the report layout windows, thus preventing Xtrieve PLUS from terminating. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: GROUP FIELD, GROUP SUMMARY, REPORT FIELD, REPORT SUMMARY Problem Fixed by This Patch: If you use a report field in a report field summary or a group field in a group field summary, Xtrieve PLUS does not allow you to remove or modify the field. This patch ensures that Xtrieve PLUS allows you to remove or modify such fields. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: FORM/ADD EDIT SCREEN, INVALID RECORD Problem Fixed by This Patch: If you attempt to add an invalid record using the Form/Add edit screen, Xtrieve PLUS exits the Form/Add edit screen and returns to the Form menu. This patch ensures that if an error occurs when you attempt to add a record, Xtrieve PLUS remains at the edit screen. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: REPORT LAYOUT Problem Fixed by This Patch: When XQL and Btrieve are loaded by Xtrieve PLUS, report layouts may become corrupt in memory after you print a report. This patch ensures that Xtrieve PLUS correctly maintains report layouts. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: HANG, REMOVE GROUP Problem Fixed by This Patch: If you remove a group from a report and then attempt to remove another group, Xtrieve PLUS displays a repetitive list of groups from which to choose. In addition, if you choose one of the listed groups, Xtrieve PLUS causes the workstation to freeze. This patch ensures that Xtrieve PLUS correctly displays lists of groups. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: BLANKS, IMPORT DATA, SDF Problem Fixed by This Patch: Xtrieve PLUS incorrectly imports data in Standard Data Format (SDF) if blanks separate the data elements, as in the following example: "Firstname", "Middlename", "Lastname" This patch ensures that Xtrieve PLUS correctly imports SDF data. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: LVAR, NOTE, TRANSLATE, VARIABLE-LENGTH FIELDS Problem Fixed by This Patch: Xtrieve PLUS does not correctly process view-to-view translations on variable-length fields that are not of the same type. For example, you cannot accurately translate a note field into an lvar field. This patch ensures that Xtrieve PLUS correctly performs such translations. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: CREATE FILE, PAGE, PREALLOCATION Problem Fixed by This Patch: When you are creating files, Xtrieve PLUS allows you to preallocate no more than 32,767 pages. This patch ensures that Xtrieve PLUS allows you to preallocate up to 65,535 pages. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: BTRIEVE, NEW COMMAND LINE OPTIONS, UNLOAD, XQL Problem Fixed by This Patch: Xtrieve PLUS does not unload Btrieve or XQL from memory if you loaded Btrieve or XQL before you entered Xtrieve PLUS. If you do not have the utilities BUTIL or NSUTIL, you cannot unload XQL or Btrieve from memory. This patch makes available two new command line options you can specify when you load Xtrieve PLUS: /ua Unloads both XQL and Btrieve when you exit Xtrieve PLUS /ux Unloads only XQL when you exit Xtrieve PLUS * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: CONDITIONAL, FIELD LIST, SCALAR FUNCTIONS, USER-DEFINED FIELDS Problem: Xtrieve PLUS may not display all available fields in a field list when you are defining a user-defined field that includes nested conditions or nested scalar functions, as in the following example expression: Result = SUBSTRING( SUBSTRING( SUBSTRING( Field3,5,20),2,Field2),5,Field1) Workaround: For each level of nesting, create a temporary, user-defined field, as in the following example: TempField1 = SUBSTRING( Field3,5,20) TempField2 = SUBSTRING( TempField1,2,Field2) TempField3 = SUBSTRING( TempField2,5,Field1) Since Xtrieve PLUS embeds the temporary field definitions in the substring field that references it, you can delete the interim temporary fields, resulting in a single, user-defined field, as in the following example: Result = TempField3 * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: DECIMAL POINTS, INTEGER FIELDS, MASKS Problem: If you place a mask that contains decimal points (such as ZZZ,ZZ9.99) on an integer field, you may get unexpected results in report summary fields. For example, if the field's data is 38,470.00, the masked result is 384.70. Workaround: Masks on integer fields should not contain decimal points. Use a more appropriate data type, such as decimal, float, money, or numeric. * * * * * * * * * Product/Platform: DOS - XTRIEVE.PDB Search Strings: PRINTER, TABLOID SETTING Problem: The Tabloid setting of the XTRIEVE.PDB file specifies the Epson LQ-1500/2.0 printer instead of the IBM PC graphics printer. Workaround: Change the Tabloid setting as follows. 1. At a DOS workstation, enter SLATE XTRIEVE.PDB. 2. In the SLATE utility, follow these steps to set the Tabloid setting: a. Select the Add/Edit Devices (Ptr Connections) option from the main menu. b. Select the 3001 Tabloid option from the Devices menu. c. Use the Tab key to move to the Ptr Mfg field and press F9 to display a list of printer manufacturers. d. Select IBM. e. Use the Tab key to move to the Ptr Type field and press F9 to display a list of printer types. f. Select PC Graphics Printer. 3. To exit SLATE, press F10 three times. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: 3, HANG, OPEN VIEWS Problem Fixed by This Patch: The MAKE_XTA utility hangs or returns Status Code 3 (File Not Open) when you attempt to open certain views. This patch ensures that MAKE_XTA can open such views. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: FIELD NAMES, LOWERCASE, UPPERCASE Problem Fixed by This Patch: The MAKE_XTA utility converts all letters in user-defined field names to uppercase. This patch ensures that MAKE_XTA preserves lowercase letters in field names. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: EQJOIN, EQUAL, JOIN, KEYWORD, NULL, NULLJOIN Problem Fixed by This Patch: The MAKE_XTA utility inserts incorrect keywords in .XTA files that contain file joins. For example, MAKE_XTA uses the keyword EQUAL when it should use the keyword EQJOIN. This patch ensures that MAKE_XTA inserts the correct keywords. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: ADD KEYWORD, REPORT LAYOUT, SUM Problem Fixed by This Patch: If a report layout contains the calculation type SUM, the MAKE_XTA utility inserts an extra .ADD. keyword in the XTA file. This patch ensures that MAKE_XTA inserts the correct number of .ADD. keywords. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: ADJACENT FIELDS, BIT FIELDS Problem Fixed by This Patch: If a dictionary contains more two or more adjacent fields of type bit, the MAKE_XTA utility inserts only the first bit field in the .XTA file. This patch ensures that MAKE_XTA inserts all bit fields. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: AUTOINC, INDEX ATTRIBUTES Problem Fixed by This Patch: The MAKE_XTA utility incorrectly extracts the index attributes of fields of type autoinc. This patch ensures that MAKE_XTA retains index attributes as defined in the original file. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: EXTRACT FILES, SUPPLEMENTAL INDEX Problem Fixed by This Patch: The MAKE_XTA utility fails when attempting to extract files that contain supplemental indexes. This patch ensures that MAKE_XTA correctly extracts supplemental indexes. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: DESCRIPTIVE FILENAME Problem Fixed by This Patch: If a descriptive filename is shorter than the actual filename, the MAKE_XTA utility pads the rest of the descriptive filename with characters from the actual filename. For example, given a descriptive filename of FILE and an actual filename of TESTING, MAKE_XTA converts the descriptive filename to FILEING. This patch ensures that MAKE_XTA inserts the correct descriptive filename into the generated .XTA file. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: EXTRACT VIEWS, USER-DEFINED FIELDS Problem Fixed by This Patch: The MAKE_XTA utility incorrectly extracts views containing relatively large user-defined fields. This patch ensures that MAKE_XTA correctly extracts such views. * * * * * * * * * Product/Platform: DOS - XCFP.EXE, v4.11 Search Strings: COMMANDS WITH NUMERALS, PAGE SIZE Problem Fixed by This Patch: The Xtrieve PLUS Command File Processor (XCFP) utility does not recognize the command that specifies page size since the command begins with a numeral. This patch ensures that XCFP recognizes commands that begin with numerals. * * * * * * * * * April 1993 Patches ------------------ The following information describes patches released in April 1993. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: MAXIMUM NUMBER OF VIEWS (819), MEMORY ERROR, /V STARTUP OPTION Problem Fixed by This Patch: Xtrieve PLUS returns a memory error on View Release and/or Retain operations when you specify more than 819 views. This patch ensures that when you specify more than 819 views for the /V startup option (for example, /V:850), you receive the following message: Xtrieve: Invalid view parameter * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: INVALID COMMAND-LINE PARAMETER, TEMPORARY FILES, XTRTMP_M.* FILE Problem Fixed by This Patch: When you supply Xtrieve PLUS with an invalid command-line parameter, the program removes all temporary files except the XTRTMP_M.* file. This patch ensures that Xtrieve PLUS correctly deletes all temporary files. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: BFLOAT DATA TYPE, RESTRICTION Problem Fixed by This Patch: Since Xtrieve PLUS v4.11b does not insert a bfloat data type correctly, any restriction based on a bfloat data type returns invalid results. This patch ensures that Xtrieve PLUS recognizes the version of the program that you are using and correctly adapts the input value to work in that environment. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: EXITING XTRIEVE, SUSPENDED COMMAND FILE Problem Fixed by This Patch: When you use a CTRL+Break key sequence while an Xtrieve PLUS command file is suspended, Xtrieve PLUS causes you to exit from the program. This patch ensures that Xtrieve PLUS stops the command file execution rather than exiting from the program. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: 2101, /D OPTION, DATA DICTIONARY, DICTIONARY SHOW, NSREQ Problem Fixed by This Patch: When you use the NetWare SQL Requester (NSREQ.EXE or NSREQS.EXE) to access dictionaries through Xtrieve PLUS and the Dictionary Show command does not display any dictionaries, restart the Requester and specify a larger length for the data message with the /D option (Date Message Length). The Show Dictionary command then displays a list of all available dictionaries. This patch ensures that the NetWare SQL Requester displays Status Code 2101 (Data Message Buffer Is Too Small) when a request to read Xtrieve data, such as a list of dictionaries, fails. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: 248, BLANKS, CHARACTER FIELD/LIST, INSERT Problem Fixed by This Patch: When you press Enter on a character field in an insert screen for which you have defined a character list and no data is shown, Xtrieve PLUS returns Status Code 248 (Invalid Size for Data Type) even if blanks are permitted in that field. This patch ensures that Xtrieve PLUS handles such character fields correctly. * * * * * * * * * Product/Platform: NetWare SQL - XTRIEVE.EXE, v4.11 Search Strings: GROUP/SUMMARY, REPORT LAYOUT, TRAP ERROR Problem Fixed by This Patch: When you choose Group/Summary in the Report Layout, Xtrieve PLUS receives a trap error (the result of incorrectly initializing the Group/Summary element), which may occur in all three environments (NetWare SQL, DOS, and OS/2). This patch ensures that Xtrieve PLUS handles the Group/Summary element correctly. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: BRACKETED CONDITIONAL FIELD, CONSTANT, USER-DEFINED FIELD Problem Fixed by This Patch: The MAKE_XTA utility does not properly convert constants when extracting a view containing a user-defined field that includes a bracketed conditional field. This patch ensures that MAKE_XTA handles such user-defined fields correctly. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: COMMAND FILE, DEFINED VIEW, JUSTIFICATION, XCFP Problem Fixed by This Patch: When you use the MAKE_XTA utility to extract a defined view and then use the Xtrieve Command File Processor (XCFP) to make that view into a command file, Xtrieve drops the left/right/center justification. This patch ensure that the MAKE_XTA utility places the correct justification information in the .XTA file. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: FIELD, FLOATING POINT VALUES, MASKABLE DATA TYPE, UNFORMATTING DATA Problem Fixed by This Patch: The MAKE_XTA utility is not handling maskable data type fields correctly, causing an invalid mask when unformatting data. In addition, the utility is not translating floating point values correctly. This patch ensures that the MAKE_XTA utility handles both maskable data type fields and floating point values correctly. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: HEWLETT PACKARD LASERJET PRINTER, VARIABLE-WIDTH FONTS Additional Printer Information: Variable-width fonts for the Hewlett Packard series of Laserjet printers do not work correctly with Xtrieve PLUS. * * * * * * * * * December 1993 Patches --------------------- The following information describes patches released in December 1993. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: GROUP, HANG, REMOVE, SUMMARIES Problem Fixed by This Patch: Xtrieve does not successfully remove a report group that contains a group summary. This occurs when you use GROUP/REMOVE from the Report menu to remove from a report a group containing other groups that themselves contain group summaries. When you again choose GROUP/REMOVE, Xtrieve displays the remaining group names multiple times in the list of groups. If you then try to remove any of the remaining groups, the computer hangs. This patch ensures that Xtrieve handles this type of operation correctly. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: HANG, PRINT, REPORT Problem Fixed by This Patch: When you attempt to print a report that contains groups, the printer occasionally hangs after printing the first page. This problem occurs, however, only when you position the groups so that subsequent groups print on the same line as the first group. In that case, Xtrieve tracks the current line and column positions inaccurately, attempts to place too much information on a page, overwrites memory, and causes the workstation to hang. This patch ensures that Xtrieve properly tracks current line and column positions. NOTE: If a group contains any fields, do not define group control fields with a line position of +0. In most cases, this operation does not produce the intended printed results. Instead, define the group with a line position of +1, which places each occurence of the fields in the group on a new line. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: EMPTY FIELD, NOTE, SDF, TRANSLATE Problem Fixed by This Patch: When translating a view including a NOTE or LVAR field that contains no data into SDF format, Xtrieve produces a field value of (HEX) 0xF9 in double quotation marks. This patch ensures that Xtrieve translates the value as "" with no data included between the quotes. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: 221, USER-DEFINED FIELD Problem Fixed by This Patch: Xtrieve returns a Status Code 221 (Invalid Syntax for Expression or Restriction) when building an expression for a user-defined field. This patch ensures that Xtrieve always zero-terminates a user-defined field expression before sending that expression to NetWare SQL for processing. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: LOADING WITH /? OR /H, XTRTMP_*.*, ZERO BYTES Problem Fixed by This Patch: When you load Xtrieve with the /?, or /h parameters, it leaves XTRTMP_M.* and XTRTMP_L.* files with zero bytes in the XTRTMP directory. This patch ensures that Xtrieve always removes XTRTMP_*.* files when it terminates. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: F1, HEAP SPACE, HELP Problem Fixed by This Patch: Xtrieve occasionally returns the message "Out of local heap space" when you press F1 for help. This patch ensures that Xtrieve always reserves enough space in memory for the help text. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: EXTRA 0, FLOAT, MASK Problem Fixed by This Patch: Xtrieve adds an extra zero following the decimal point to float values when the display mask for those values contains the special () literals. This patch ensures that these special literals do not affect the number of digits following the decimal point. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: BORDER COLOR, CONFIGURE, USE BIOS SWITCH Problem Fixed by This Patch: When you change the color of the border to a color other than black (the default), Xtrieve does not reset the color to black when it exits. This patch ensures that the border color is reset to black when Xtrieve exits, provided that the Use BIOS switch is turned off. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: EXTRA BLANK PAGE, PRINT DEFINITION Problem Fixed by This Patch: When you print a definition (view, report, or dictionary table), Xtrieve prints an extra blank page before printing the actual definition. This patch ensures that the first printed page is the first page of the definition. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: CONDITIONAL, USER-DEFINED FIELD Problem Fixed by This Patch: Xtrieve does not properly define a user-defined field if its definition is based on a conditional statement and other user-defined fields. The problem occurs when you include in the definition a condition that compares two user-defined fields. This patch ensures that Xtrieve includes the correct fields in a conditional user-defined field and correctly defines the entire field. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: DEFINITION, PRINT, VIEW Problem Fixed by This Patch: When printing a large view definition, such as one with many joined files, Xtrieve displays the following error message: "Error writing output." This patch ensures that Xtrieve allocates a buffer large enough to handle multiple joined file views so that you can print the definition of such a view. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: DICTIONARY, INDEX, PRINT, SHOW Problem Fixed by This Patch: If you drop an index from a table definition and do not renumber the remaining indexes, Xtrieve does not display the definitions for indexes with a number higher than the one that was dropped. This patch ensures that Xtrieve correctly finds all index definitions when showing or printing a table definition. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: COMPLETE, RESTRICT, VARIABLE FIELD Problem Fixed by This Patch: In some cases, you cannot complete a restriction when that restriction includes a variable length field because Xtrieve occasionally overwrites memory in this situation. This patch ensures that no memory overwrite occurs, enabling you to complete the restriction. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: DICTIONARY, TABLE DEFINITION, VOLUME NAME Problem Fixed by This Patch: Xtrieve does not allow you to include a volume name in the path to the Btrieve data file for a table definition. This patch ensures that you can enter any of the following for the location for a table definition: \\server\vol:directory\file vol:directory\file drive:directory\file directory\file file * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: 213, OWNER NAME, VIEW Problem Fixed by This Patch: Xtrieve displays Status Code 213 (Read Access) when the XTROWNER variable does not contain the owner name(s) required to recall a view definition. This patch ensures that Xtrieve requests the owner names when recalling a view just as it does when opening a table for a view. The only difference is that Xtrieve asks for an owner name each time after you press Enter until you press ESC, or until you press Enter if you have not typed a name at the prompt. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: /D PARAMETER, /K PARAMETER, COMMAND FILE, KEYBOARD FILE, LOADING XTRIEVE Problem Fixed by This Patch: Xtrieve does not load successfully when you specify a keyboard input file along with the /D parameter. This patch ensures that you can load Xtrieve when you specify the /D parameter and a keyboard input file, provided that you also specify either the /K parameter or a command file. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: DATE FIELD, DIF FILE, LOTUS 123 Problem Fixed by This Patch: When Xtrieve translates a date field into a DIF file format and you then load the DIF file into Lotus 123, the date value appears as ******. (This problem occurs only when Xtrieve is loaded and you are using XQLP 2.x.) This patch ensures that Xtrieve correctly translates the date values to the DIF file format. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: 227, USER-DEFINED FIELD Problem Fixed by This Patch: When the menu for a user-defined field definition is full and cannot hold any additional entries, Xtrieve displays Status Code 227 (Operand Must Be a Dictionary Field) when completing the definition. This patch ensures that Xtrieve correctly tracks the table name for a field when the menu is full and then builds the definition correctly. * * * * * * * * * Product/Platform: DOS - XTRIEVE.EXE, v4.11 Search Strings: LOAD RECORD AND RELATIONAL MANAGERS Problem Fixed by This Patch: Xtrieve does not load successfully when you attempt to load it with both the Btrieve Record Manager and the XQL Relational Manager. This patch ensures that Xtrieve successfully loads both programs. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: COMMAND FILE NOT REPLAYABLE, REPORT LAYOUT DEFINITION, XCFP Problem Fixed by This Patch: When MAKE_XTA extracts a report layout definition and XCFP converts that .XTA file to an .XTC file, Xtrieve returns the error message "Command file contains keystroke which is not replayable," and the command file does not complete. This patch modifies the way in which MAKE_XTA builds .XTA files for report layouts so that the command file contains valid keystrokes and builds the correct report. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: APPEND, BRACKET COMMAND, CONCATENATE, USER-DEFINED STRING FIELD Problem Fixed by This Patch: When converting a user-defined field into an .XTA file, MAKE_XTA adds a .BRACKET. command when it attempts to append one string to another string or to concatenate two strings. This patch ensures that MAKE_XTA does not insert a .BRACKET. command when converting a user-defined string field. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: FIELD HEADINGS AND OFFSETS, VIEWS Problem Fixed by This Patch: When MAKE_XTA converts a view, it occasionally uses the field names, rather than the user-specified headings, for the fields in the view. Also, MAKE_XTA does not insert the correct field offset. This patch ensures that MNAKE_XTA employs the user-specified field heading for all fields and inserts the correct field offset. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: MULTIPLE FIELD NAMES, TABLE NAMES, VIEWS Problem Fixed by This Patch: When MAKE_XTA converts a view, it does not select the correct occurrence of a field when the field name appears more than once in the view. (This occurs because MAKE_XTA does not accurately determining the correct table name for the field.) This patch ensures that when you are rebuilding a view definition, MAKE_XTA determines the correct table name whenever you select a field name from a menu. * * * * * * * * * Product/Platform: DOS - MAKE_XTA.EXE, v4.11 Search Strings: COMMAND FILE, ESC COMMANDS, FOOTER, HEADER Problem Fixed by This Patch: When a report contains a header or footer, MAKE_XTA does not place the correct number of .ESC. commands in the command file. As a result, the command file does not replay correctly in Xtrieve. This patch ensures that MAKE_XTA places the correct number of .ESC. commands in the command file for report headers and footers. * * * * * * * * * Product/Platform: DOS - XCFP.EXE, v4.11 Search Strings: COMMAND FILE, FMENU COMMAND, XTA TO XTC CONVERSION Problem Fixed by This Patch: When XCFP converts an .XTA file containing an .FMENU. command to an .XTC file, XCFP does not place the commands in the command file. This patch ensures that XCFP correctly interprets an .FMENU. command and includes it correctly in the .XTC file. * * * * * * * * * ================================================================================ Documentation Updates ===================== The following sections contain documentation updates for the "Xtrieve PLUS User's Manual" and the "Xtrieve PLUS Tutorial." NOTE: The documentation updates that follow supplement any documentation updates noted in the Readme file of the original product. Note that only the December 1992 patch release included such updates. December 1992 Updates --------------------- Note the following changes to the "Xtrieve PLUS User's Manual:" - Page vi Replace the section "Where To Get Help" with the following: Where To Get Help Novell offers support through a wide range of programs. This section lists sources of help that are available for the Novell Database Products line. Telephone Technical Support Novell's telephone technical support program provides helpful information about getting the best results from your Novell product. Refer to the section "Contacting Novell" for information about contacting Novell for technical support. If you are contacting Novell for a follow-up on a previous technical support issue, please be ready to provide your open call reference number. International Technical Support International customers may find the Direct Connect (SM) Fax International program useful. This program provides priority handling of fax support, which allows international customers to obtain technical support without worrying about high telephone costs and time zone differences. Novell encourages customers who reside outside the continental United States and Canada to contact their local Novell office or Novell authorized reseller for more information about international support options. Refer to the section "Contacting Novell" for the fax number for international technical support. Product Information The Developer Relations department at Novell Austin can provide information about Novell Database Products, technical support programs, and the Novell Professional Developers' Program. You can request detailed product information from the automated fax system or speak to a trained technician about product announcements, pricing, compatibility, services, and developer issues. CompuServe Forum You can find information about Novell Database Products under the NetWire section on CompuServe. NetWire provides 24-hour-a-day electronic information services. You can obtain the most recent online technical notes, problem reports and fixes, product news, and other helpful information. You can also post technical questions and receive answers from our technical support staff. If you already have a CompuServe account, type GO NOVELL to access the NetWire section. For information about subscribing to CompuServe, contact CompuServe, Inc. at 1-800-848-8199 (or 1-614-457-0802 in Ohio or outside the U.S. and Canada). Contacting Novell Novell has established a comprehensive services strategy to support all network users and systems--small or large, domestic or international. We welcome hearing from you. The mailing address for Novell Austin is as follows: Novell, Inc. 5918 W. Courtyard Drive Austin, Texas 78730-5036 U.S.A. To contact us by telephone or fax, refer to the following table for the appropriate number. For Contact Telephone Fax ------------------------------------------------------------------------ Technical Support Novell Services 1-800-NETWARE 1-512-794-1775 International (1-800-638-9273) Technical Support or 1-801-429-5588 outside the U.S. Product Novell Austin 1-800-RED-WORD 1-512-345-7478 Information* Developer (1-800-733-9673) Relations or 1-512-794-1796 outside the U.S. General Inquiries Novell Austin 1-512-346-8380 1-512-345-7478 Receptionist * International customers can contact their local reseller for Novell Database Products information. - Page 1-13 Add the following note before the last paragraph of the section "Using Xtrieve PLUS with Btrieve and XQLP": Note: The null file handles that are created when Xtrieve PLUS automatically loads Btrieve and XQLP are not released when you quit Xtrieve PLUS. Depending on how high you set the FILES variable in your CONFIG.SYS file, there may not be any DOS file handles available when you attempt to start another application. If this condition occurs, you must restart your computer before you can run another application. - Page 1-16 Add the following parameter: /r<y|n> Tells Xtrieve PLUS whether to restore the original VGA state after the VGA state is changed temporarily. Some VGA video adapters cause unexpected results when Xtrieve PLUS attempts to restore the VGA state after it has been changed. The /rn option tells Xtrieve PLUS not to restore the original VGA state after the state has been changed. The /ry option (the default) tells Xtrieve PLUS to restore the original VGA state. - Page 1-17 The description of the /w option should read as follows: Specifies the maximum view width (in bytes) that Xtrieve PLUS allows. The view width is determined by combining the length of each field in the view. However, if a field's heading is longer than the field itself, use the length of the heading in your calculation. You can specify from 4 to 8,192 bytes. For example, the following parameter specification allows a view width of up to 256 bytes: /w:256. If you do not specify this option, Xtrieve PLUS uses a default value of 1,024 bytes. The larger the view width you specify, the fewer records Xtrieve PLUS can display on the screen at one time. - Page 1-18 Add the following note after the first paragraph of the section "Using the /k Option to Read a Keyboard Input File": Note: If the keyboard input file includes a directory path, use a double backslash to represent a single backslash. For example, the path \XTRIEVE\DEMODATA would be represented as \\XTRIEVE\\DEMODATA in the input file. - Page 1-19 The first paragraph in the section "Using the MAIN Menu" should read as follows: After you start Xtrieve PLUS, the MAIN menu appears on your screen, as shown in Figure 1.4. If you are using a mouse, a small block appears in the upper left corner of the screen. This block indicates the mouse is enabled. Also, the mouse cursor appears in the center of the screen (not shown in Figure 1.4). - Page 2-38 The section "Printing Wide Views" should read as follows: Printing Wide Views If your view is wider than 80 characters, you cannot print all of it at one time (unless your printer can handle more than 80 characters per line). You must perform multiple print operations to print the view. That is, print the first 80 characters, and then define a new offset value from the PRINT OPTIONS menu to print subsequent characters (in groups of 80 characters per print operation). To print a wide view, proceed as follows: 1. For the first print operation, choose Print from the VIEW menu, select Yes from the DEFAULTS menu, and enter the device name in the DEVICE NAME box to send the view to the printer. 2. For the second print operation, choose Print from the VIEW menu. 3. When the DEFAULTS menu appears, select No. 4. When the PRINT OPTIONS menu appears, accept the defaults until you get to the Offset option. Enter 80 for the offset. If additional print operations are necessary, repeat Steps 2 through 4, adding 80 to the offset each time until the entire view is printed. - Page 3-15 In Table 3-1, the description of a Null join should read as follows: Include all records from the primary file even if they have no matching records with the secondary file. - Page 3-19 Add the following note to the end of the section "Translating to an External Format": Note: If you use the Translate to DIF option to import dates into Lotus 1-2-3 from a file created by Xtrieve PLUS v4.10 or v4.11, the dates will be wrong by one day. This is because Xtrieve PLUS uses the date 01/01/1900 as day 0, whereas Lotus considers the same date as day 1. To convert the data to the proper date, use a formula in your Lotus spreadsheet to subtract one from the date. - Page 4-6 Add the following note at the end of the section "Absolute and Relative Positioning": Note: If the position of the first report item on a page (not including the heading) is set using absolute line positioning or using a relative line position of +0, Xtrieve PLUS places each occurrence of that report item on a new form, even if the NEW FORM option is set to No. - Page 4-13 In the last paragraph of the section "The Report Layout Screen," the sentence that begins "If you press Shift+F8" should read as follows: If you press Shift+F8 while the Report Layout screen is displayed in Prompt mode, you can see the line type for each line (header, detail, footer) in the left margin, as Figure 4.6 shows. - Page 5-4 Add the following note before the third bullet: Note: You cannot assign a mask to a date that prints as a result of the @date text directive; the date prints using the default date mask (mm/dd/yy). If you want to apply a mask to the date in your report, add a user-defined date field to the view on which your report is based, and specify CURRENT as the field's definition. This field will always contain the current date. When you position the field in the report, Xtrieve PLUS asks you to specify a mask. - Page 7-24 Add the following note after the first paragraph of the section "Defining Supplemental Indexes": Note: You cannot define or remove a supplemental index for a file that is active in a view. Release the file before attempting either operation. - Page 7-24 Step 2 in the section "Defining Supplemental Indexes" should read as follows: 2. Select the file for which you want to define a supplemental index. The menu that appears lists three options: Show, Define, and Remove. (If you select a file that is currently active, the only option available is Show.) - Page 7-25 The first paragraph in the section "Removing Supplemental Indexes" should read as follows: To remove a supplemental index for a file, complete the following steps. (Remember, you cannot remove a supplemental index for a file that is active in a view.) - Page 7-25 Step 2 in the section "Removing Supplemental Indexes" should read as follows: 2. Select the file for which you want to remove a supplemental index. The menu that appears lists three options: Show, Define, and Remove. (If you select a file that is currently active, the only option available is Show.) - Page 10-5 Replace the first sentence after Table 10.1 with the following: Xtrieve PLUS supports landscape printing. Refer to the section "Defining Printer Devices" on page 10-7 for information about creating a device that allows you to print in landscape mode. - Page 10-8 Add the following note after Step 6: Note: Some printer manufacturers list a separate printer type for landscape printing. For those printer types, the printer database displays (LS) as part of the type name. Ensure that you choose the landscape printer type, where appropriate. - Page 10-8 Add the following note after Step 8: Note: If you are defining a device that allows you to print in landscape mode, modify the settings under Paper Setup as follows: Paper Length: 8.50 in Paper Width: 11.00 in Under Defaults, set the top and bottom margins to a minimum of .10 inches, and set the left and right margins to a minimum of .25 inches. - Page 10-25 Replace the description of the Display Width parameter in Table 10.4 with the following: Defines the maximum record width used in a view. The default is 1,024. The maximum allowed is 8,192. - Page 11-19 The last paragraph in the section "Setting Environment Variables Using the Set Command" should read as follows: Replace variable with one of the 11 Xtrieve PLUS environment variables. Do not insert a space on either side of the equal sign (=). If you want to negate a previous setting, issue the SET command as follows, replacing variable with one of the 11 Xtrieve PLUS environment variables, but without specifying a value. SET variable = The following sections explain how to set each of the Xtrieve PLUS environment variables with the SET command. - Page 11-22 Replace the section XTRPATH with the following: XTRPATH Xtrieve PLUS searches for your data files in the location specified in the dictionary, or in the location specified in the dictionary and the XTRPATH environment variable. Xtrieve PLUS ignores the XTRPATH variable if the location specified in the dictionary begins with a backslash (\) or a drive letter, thus enabling you to use the dictionary alone to specify the complete path to search for the data files. However, if you need to accommodate different location names based on users' drive mappings, you should use the XTRPATH environment variable in conjunction with the dictionary to specify the data file location. If you use the XTRPATH variable, ensure that the file location specified in the dictionary is complementary to the path specified in XTRPATH. Depending on where you run Xtrieve PLUS, the XTRPATH variable can be used in a number of ways, as follows: Data File Location XTRPATH Specified in Dictionary Comment ----------------------------------------------------------------- F:\TEST\DATA MYFILE.BTR Works in all cases \TEST\DATA MYFILE.BTR Works if running Xtrieve PLUS from F: TEST\DATA MYFILE.BTR Works if running Xtrieve PLUS from F:\ To avoid binding users to a particular drive mapping and directory for their data file location, you should use XTRPATH to specify the drive and as much of the path as possible, specifying only the filename in the dictionary. In the preceding example, if the file MYFILE.BTR resides on F:\TEST\DATA, you should set XTRPATH to F:\TEST\DATA and specify MYFILE.BTR as the data file location in the dictionary. However, in some cases, you may want to specify only part of the path in XTRPATH. If you intend to store data files in several subdirectories with the same name but with different paths, specify the variable portion of the path in XTRPATH; use the dictionary to specify the subdirectory where the data files reside. You can also use the XTRPATH variable to instruct Xtrieve PLUS to search multiple directories for data files. Use a semicolon to separate the directories. For example, to instruct Xtrieve PLUS to search the directories F:\DATA and G:\FILES for data files, set XTRPATH as follows: SET XTRPATH = F:\DATA;G:\FILES If you modify XTRPATH from within Xtrieve PLUS and then save the configuration, Xtrieve PLUS stores the modified value with the configuration file. However, the value stored in the operating system environment takes precedence over the value stored in the configuration file. - Page A-1 Replace the note in the section "Xtrieve PLUS Error Messages" with the following: Note: If the Xtrieve PLUS message file is not available, Xtrieve PLUS displays the following message: Xtrieve message file not loaded. Error code = xxxx In this message, xxxx represents an internal code. If you receive this message and you want Xtrieve PLUS to display textual error messages, you can either place the message file (XTRIEVE.MSG) in the directory from which you started Xtrieve PLUS or set the XTRMSG environment variable to indicate the directory that contains the Xtrieve PLUS message file. (For more information on the XTRMSG environment variable, see Chapter 11, "Configuring Xtrieve PLUS.") You must restart Xtrieve PLUS for either of these changes to take effect. Thereafter, when an error condition occurs, Xtrieve PLUS PLUS displays one of the textual error messages described in this appendix. - Page A-4 Add the following message and description: Dictionary is Empty Xtrieve PLUS cannot access the dictionary files, or no dictionary files exist. Either modify the configuration to specify the location of the dictionary files, or create dictionary files in the directory where Xtrieve PLUS is configured to find them. - Page A-7 Add the following message and description: Error Setting Field Attribute, Status = n In Xtrieve PLUS, Status Code n was returned when you set a field attribute. - Page A-8 Add the following message and description: File Does Not Have Any Fields which May Be Used in an Index In Xtrieve PLUS, you have attempted to define an index in a file in which all of the fields are of the data type bit. A bit type field cannot be used as an index. Either define a field of a data type other than bit and then use it in an index, or make the file a data-only file. - Page A-10 Add the following message and description: Insufficient Memory in Xtrieve to Show All Fields Xtrieve PLUS returns this message when there is not enough memory available to hold the field definitions you have specified. To make more memory available, unload any TSRs that are not in use. Alternatively, if your workstation has expanded or extended memory, you can use your memory management program to move TSRs or applications to high memory. - Page A-10 Add the following message and description: Invalid Temporary Storage Directory. Directory Must Exist Xtrieve PLUS used the directory specified in the XTRTMP environment variable to store temporary files that hold session-specific information. Either create the directory you specified, or reset the XTRTMP variable to an existing directory. - Page A-11 The message "Missing or invalid 'col' specification in text window file" should read "Missing or Invalid '@xxxxx' Specification in Text Window File." The explanation of this message should read as follows: In Xtrieve PLUS, the specification for the column location, row location, or width value in the text window file is either invalid or missing. Correct the value, or supply it if it is missing. - Page A-12 The message "Missing or Unrecognized Menu Definition File" should read "Missing or Invalid Menu Definition File." The explanation of this message should read as follows: Either Xtrieve PLUS attempted to use an old version of the menu definition file (XTRIEVE.MEN), or it cannot find the menu definition file. Ensure that you are using the version of the menu definition file contained on your Xtrieve PLUS diskettes. Also, this file must be located in either the current directory or the directory specified in the configuration file (using the XTRMEN environment variable) as the location for the menu definition file. - Page A-12 Add the following message and description: Money Fields May be from 2 to 10 Bytes Inclusive In Xtrieve PLUS, you defined a money type field with a size less than 2 or greater than 10. Modify the size of the field so that it is within the valid range. - Page A-15 Add the following message and description: Numeric Fields May be from 1 to 15 Bytes, Inclusive In Xtrieve PLUS, you defined a numeric type field with a size less than 1 or greater than 15. Modify the size of the field so that it is within the valid range. - Page A-15 Add the following message and description: Out of File Handles. Increase 'FILES=' Parameter in CONFIG.SYS Xtrieve PLUS cannot assign a DOS handle to open the file. Increase the 'FILES=' parameter in the CONFIG.SYS file. - Page A-17 Add the following message and description: Please Specify an Integer Value Between 0 and 10, Inclusive The value specified for the Delay Time option on the CONFIGURE/PARAMETERS menu tells Xtrieve PLUS how many tenths of a second to delay when replaying command files. This value must be an integer between 0 and 10, inclusive. - Page A-17 Add the following message and description: Please Specify an Integer Value Between 4 and 8192, Inclusive In Xtrieve PLUS, the value specified for the Display Width option on the CONFIGURE/PARAMETERS menu defines the maximum record width used in a view. This value must be an integer between 4 and 8,192, inclusive. - Page A-17 Add the following message and description: Please Specify an Integer Value Greater than 0 In Xtrieve PLUS, the values specified for the Views, Fields, and Report Items options on the CONFIGURE/PARAMETERS menu define the maximum number of active views, the maximum number of active fields in all views, and the maximum number of report elements in a report, respectively. For these options, you must specify an integer value greater than 0. - Page A-20 Add the following message and description: The User PUBLIC Cannot Be Removed In Xtrieve PLUS, you attempted to remove the user PUBLIC by using the Security option. Since the user PUBLIC is system defined, you cannot remove it. - Page A-22 Add the following message and description: Unable to Drop File Definition, Status = n In Xtrieve PLUS, you do not have ownership of the file. Determine the Btrieve owner name and try the operation again. - Page A-22 Add the following message and description: Unable to Drop Supplemental Index, Status = n In Xtrieve PLUS, you do not have ownership of the file for which the index is defined. Determine the Btrieve owner name and try the operation again. - Page A-22 Add the following message and description: Unable to Open Keyboard Input File If you entered /k:filename on the command line, Xtrieve PLUS is unable to find the specified keyboard input file. If you are using the XTRIEVE.CNF file to implement the /k option, ensure that XTRIEVE.CNF is not corrupted. - Page A-24 Add the following message and description: User Defined Field Cannot Be Added When There Is a Variable-Length Field When you are creating a view that includes a variable-length field in Xtrieve PLUS, the variable-length field must be the last field you define. Remove the variable-length field, add the user-defined field, and redefine the variable-length field. - Page A-24 Add the following message and description: User Input Is Required, But No Input Source Is Available In Xtrieve PLUS, you attempted to run a command file that requires keyboard input, but no keyboard input file is available. Restart Xtrieve PLUS without using the /d startup option. Alternatively, you can restart it using the /k startup option and provide a keyboard input file. (See "Running Xtrieve PLUS" in Chapter 1.) - Page A-41 Add the following Status Codes and descriptions: 207 Field Does Not Exist in the Dictionary One of the fields in the list is not defined in the currently active dictionary. Be sure you specified the names correctly and you used the appropriate character representation for a blank if the name contains embedded blanks. 208 The Position Parameter Value Is Out of Range for This Function The position you specified for a field in a field list is out of range. Valid positions are between 1 and the number of fields in the view, inclusive. - Page A-43 Add the following Status Code and description: 227 Operand Must Be a Dictionary Field The first operand in a restriction statement must be a valid field that is defined in the dictionary. - Page A-49 Add the following status codes: 349 The Specified Data Value Is Too Large for the Field Definition The data value you specified is larger than the maximum length defined for the field. 350 Security Has Not Been Enabled on This Dictionary You attempted an operation that you can do only when security is enabled. Database security is not enabled at this time. To perform the operation successfully, you must first enable security on that database. 351 A Transaction Has Not Yet Been Started You attempted to perform a COMMIT or ROLLBACK operation without being inside a transaction. You must start a transaction before you can perform a COMMIT or ROLLBACK operation. To start a transaction, issue a START TRANSACTION operation. 352 Record Count Must Be Greater Than Zero NetWare SQL received a record count value for the xFetch call that is not more than zero. The record count for an xFetch call must be at least 1. - Page D-5 The description of Bit 5 of Xi$Flags should read as follows: Index is not case sensitive. - Page E-1 Add the following parameters: /r<y|n> Tells Xtrieve PLUS whether to retain the current VGA state when the VGA state is changed temporarily. /s Identifies the NetWare SQL or XQLP session - Page E-1 Change the maximum value for the /f parameter from 511 to N/A; there is no maximum value for this parameter. Note the following changes to the "Xtrieve PLUS Tutorial": - Page 3-21 Step 2 of the section "Justifying Data in a View" should read as follows: If modifying a field, select the field you want from the MODIFY menu. If adding a field, select No from the DEFAULTS menu, and then select the field you want from the ADD menu. - Page 4-15 In the example given in Step 2 of the section "Browsing a View," reverse the values for Amt Paid and Balance Due: - Page 4-18 Step 9 of the section "Creating the Schedule View" should read as follows: 9. Select the USER DEFINED option, and then select String from the TYPE menu. Enter 35 for the field size. ================================================================================ Online Help Updates =================== This section contains updates to the Xtrieve PLUS online help system. December 1992 Updates --------------------- - Several sections of the help text indicate you can define a maximum of 119 indexes for a file. Xtrieve PLUS allows only 24 indexes per file. - The help text includes several references to the numericsts data type. However, Xtrieve PLUS does not support this data type. - In the section of the help text that discusses the Parameters option on the CONFIGURATION menu, the references to the NetWare SQL Requester and the NetWare Btrieve Requester should read XQLP and Btrieve, respectively. ================================================================================ Novell, Inc. has attempted to supply trademark information about company names, products, and services mentioned in this file. The following list of trademarks was derived from various sources. NetWare, Novell, Btrieve, and XQL are registered trademarks of Novell, Inc. NetWare Btrieve, NetWare Loadable Module, NetWare SQL, NLM, and Xtrieve PLUS are trademarks of Novell, Inc. NetWire is a registered service mark of Novell, Inc. 1-2-3 and Lotus are registered trademarks of Lotus Development Corporation. CompuServe is a registered trademark of CompuServe, Incorporated. Microsoft and MS-DOS are registered trademarks of Microsoft Corporation. ** End of XTRDOS.TXT **